…a axum

State-signature relay server, espresso-dev-node, hotshot-state-prover,
submit-transactions, and nasty-client bind axum servers with
tide-disco-compatible routes, bodies, and healthchecks (bare
HealthStatus, accept-negotiated JSON or vbs). Clients stay on
surf-disco.

Ports the remaining tide-disco servers. The orchestrator decodes
surf-disco's double-vbs-wrapped request bodies; node-metrics scrapes
node identity from /v1/status/metrics; the standalone builder's
/healthcheck stays decodable as HealthStatus by hotshot task-impls.
Clients stay on surf-disco.

The docs routes and OpenAPI finish lived only in create_router_v1,
which no serve mode calls: the serve modes compose module routers
directly, so the running node 404'd on /v1 while the unit tests
passed. Extract finish_v1_docs() and route all four serve modes
(full, fs, status, bare) through it; the generated spec now reflects
exactly the modules each mode mounts. Regression test assembles the
router the way serve_axum_status does, wrapped in the production
top-level-routes and legacy-URI-rewrite layers.

aide only derives path parameters from named-struct Path<T>
extractors; the v1 handlers all use primitives and tuples, so every
operation showed zero parameters and Swagger's try-it-out could not
fill the URL templates. Declare a required string parameter for every
{name} template segment after finish_api (string because primitive
extractors carry no type metadata; handlers parse).

Also: Swagger UI opens operations with try-it-out enabled; the
test_api example moves to port 5001 (macOS AirPlay holds 5000) and
its startup log lists the v1 doc URLs.

Numeric template segments (height, from/until, epoch, view, index,
limit, offset, namespace, finalized, ...) are declared as unsigned
integers, matching each handler's Path<T> extractor; hash, key, and
address segments stay strings. Unknown future names default to string.
Documentation-only: handlers parse the raw segment regardless.

The first path segment after /v1/ becomes the operation's OpenAPI tag,
so Swagger renders one collapsible section per module (availability,
status, catchup, ...), sorted.

Palette from the staking UI: cream background, coffee headings,
cookie-brown GET and orange POST accents; topbar hidden.

Review feedback: 44 in-function use statements move to the file
header; long v0_3/v0_4 turbofish paths shortened via imports; the
shared last_merklized_state_height comment now names all state
modules.

Review feedback: the macro now stringifies the parameter ident instead
of taking a redundant string. Also fixes namespace_proof_by_payload_hash,
whose "payload-hash" literal never matched the {payload_hash}
placeholder, leaving it unsubstituted in built paths.

Review findings. tower's concurrency permit is released at the 101
upgrade, so websockets escaped ESPRESSO_NODE_API_MAX_CONNECTIONS
entirely; a shared semaphore now gives plain requests a slot while in
flight and streaming sockets one for their lifetime, with a real-TCP
regression test.

The API port also binds before router composition: OpenAPI generation
takes ~0.5s in debug builds, and clients connecting during it now
queue in the accept backlog instead of being refused. This is what
broke the test-postgres shards: first-request test helpers panic on a
refused connection.

drive_ws_stream only noticed a dead client on the next send, so a
socket whose stream was quiet held its max_connections slot and its
stream task forever; reconnect churn exhausted the demo's budget of 25
and every plain request got 429, killing the native-demo e2e tests
(claim-rewards-loop exits on non-404 and tears the demo down). Poll
the client side with select so disconnects release the slot and end
the task immediately. Regression test now uses a never-yielding
stream.

The demo's nasty-client holds up to 100 open streams per resource type
by design, against a request budget of 25; counting sockets for their
lifetime starved every plain request on node-1 with 429 and killed the
native-demo e2e tests. max_connections goes back to bounding in-flight
requests only (as in every green run); a socket's slot is released at
the 101 upgrade. Stream tasks still end promptly on client disconnect,
which was the actual leak.